home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: Invalid Indirection???
- Date: 22 Mar 1996 14:43:57 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4ivafdINNdps@keats.ugrad.cs.ubc.ca>
- References: <4i7cck$t67@infa.central.susx.ac.uk> <4iah9k$r02@newshost.cyberramp.net> <danpop.826916016@rscernix> <4ips1j$fq0@airdmhor.gen.nz>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <4ips1j$fq0@airdmhor.gen.nz>,
- Simon Hosie <gumboot@airdmhor.gen.nz> wrote:
- >Dan Pop:
- >> For the "innocent" readers: those spaces don't make ANY difference.
- >> They improve the readability for the humans, but are irrelevant to the
- >> compilers, because neither ]* nor *temp are valid tokens. Ditto for
- >> )+, +( or )+(.
- >
- > What's wrong with *temp?
-
- What Dan Pop (who has a clue the size of Manhattan in this newsgroup, by the
- way) was clearly talking about is that ``*temp'' will never be _mistaken_ to be
- a _single_ token, whether or not you have the spaces. The lexical analyzer's
- pattern matching rules can readily separate the ``*'' from the ``temp''. You
- do need spaces between any combinations of keywords and identifiers (``inti''
- is not an acceptable contraction of ``int i'') and in other contexts where the
- pre-processor will otherwise get confused.
- --
-
-